Feature : Modify tenderduty dashboard status about tendermint bn254 pubkey type for union chain #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Personally, so many validators who is operating chains in cosmos-sdk based chains want to use tenderduty for alerting their own validator nodes' uptime or something.
However, Its funtionality is not matched with chains which will be using BN254 types key such as Union Chain.
Then, if you're a node operator in union testnet, you cannot see your node status like bottom.
Failure Examples
dashboard & uptime
logs
Because of it, I made a seond PR for tenderduty for modifying status and logs about tendermint. bn254 type and union chain.
I already knew it's not best way. But, It works!
If you have a better way, I would welcome to modify this PR. Thanks.